ci: authenticate protected catalog pushes - #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Authenticate automated catalog pushes with the repository
CATALOG_PUSH_TOKENinstead of the per-workflowGITHUB_TOKEN.Why
The catalog default branch is being protected with required PRs and CI. GitHub does not allow its built-in Actions integration to be selected as a ruleset bypass actor in this organization. The organization-admin push token provides the audited bypass used by the existing official catalog while normal human changes still go through PR checks.
Validation
GOWORK=off go test ./...GOWORK=off go run ./cmd/check-catalogCATALOG_PUSH_TOKENconfigured as an encrypted repository Actions secretAI use
Implemented and validated with OpenAI Codex under maintainer direction.